Website Builder & Publisher MCP

Created By
11cafea year ago
Overview

what is Web Builder & Publisher MCP?

Web Builder & Publisher MCP is a platform that allows users to create and publish websites using AI-generated code in a remote coding environment.

how to use Web Builder & Publisher MCP?

To use the platform, simply ask the AI to create a website, and it will generate the code for you. You can then publish it as a live URL.

key features of Web Builder & Publisher MCP?

  • Publish static HTML, JS, and CSS files as public website URLs.
  • Live code editor for real-time editing of website content.
  • Remote code sandbox for building and testing code safely.
  • Multi-file support for managing various web assets.

use cases of Web Builder & Publisher MCP?

  1. Quickly creating and deploying personal or business websites.
  2. Testing and iterating on web designs in a live environment.
  3. Educational purposes for learning web development.

FAQ from Web Builder & Publisher MCP?

  • Can I publish any type of website?

Yes! You can publish static websites created with HTML, CSS, and JavaScript.

  • Is there a limit to the number of websites I can create?

No, you can create and publish as many websites as you need.

  • How do I access my published website?

After publishing, you will receive a unique URL to access your website.

Server Config

{
  "mcpServers": {
    "runbox-website-builder": {
      "command": "npx",
      "args": [
        "-y",
        "code-sandbox-mcp@latest"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
11cafe
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago